Repository navigation
chore: correct the landing site, the development guide and repository metadata - #135
Merged
Merged
Conversation
Link the dataset at GetTechAPI/TechAPI, list the workflows that exist, and drop the Monday schedules and automated PRs: nothing runs on a schedule and collectors only produce a patch for a maintainer.
The guide still described the pre-split product: record counts, no collectors in this repo, Codespace notes and a file that is gone.
The organisation has no teams, so @GetTechAPI/maintainers matched nobody.
This repo holds no data, so the data-addition and data-correction forms become a contact link. The bug form no longer points at a hosted API.
…eckout The Dockerfile copied data/ and scripts/, which left this repo with the split, and never copied config/, which the scoring service reads. The image now expects the dataset at TECHAPI_DATA_DIR=/data and compose mounts ../TechAPI/data there read-only.
.gitignore described data/_staging and data/_verify, but this repo has no data/. .env.example listed Supabase, Sentry and Redis settings that no code reads.
The config still pointed at seungpyo1007.github.io/TechAPI, so the page published at gettechapi.github.io/TechEngine loaded its stylesheet and links from /TechAPI/.
TechEngineBot
added
bug
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Part of #100. The landing site, the development guide and the GitHub metadata still described weekly schedules, automated PRs, an old repository link and data that no longer lives here. This corrects them to how the repositories work now.
Changes
refresh-data; collectors are run by hand and produce a patch that a maintainer reviews; the workflow list shows the eight real workflows; the TechAPI link points to GetTechAPI.site/astro.config.mjsstill hadseungpyo1007.github.ioand base/TechAPI, so the page published atgettechapi.github.io/TechEngine/loads its stylesheet and internal links from/TechAPI/. It now usesgettechapi.github.ioand/TechEngine.docs/DEVELOPMENT.md: rewritten for this repository: real commands, all routes, no stale counts.data/andscripts/, which do not exist here; the image reads the dataset fromTECHAPI_DATA_DIR=/data, anddocker-compose.ymlmounts a sibling TechAPI checkout'sdata/there read-only. This was reasoned from the files and has not been built..env.exampleentries for things the code never reads.Checks